In `@src/components/Trackpad/TouchArea.tsx`:
- Around line 3-8: TouchAreaProps declares isTracking but the TouchArea
component never consumes it; remove the unused required prop or make it optional
to avoid forcing callers to pass a noop value. Update the TouchAreaProps
interface by deleting the isTracking: boolean entry (or change it to
isTracking?: boolean) and then run a quick search for TouchAreaProps/type usages
to adjust any call sites or tests that currently supply isTracking so they no
longer must provide it; ensure handlers and status remain unchanged.

In `@src/hooks/useTrackpadGesture.ts`:
- Around line 52-61: The setTimeout in onDragEnd can call send after unmount;
fix by tracking the timeout ID in the useTrackpadGesture hook (e.g., a timeoutId
ref) and either clearTimeout(timeoutId.current) before scheduling and on the
hook cleanup, or add a mounted ref check that prevents calling send if
unmounted. Update onDragEnd to store the returned timer id when scheduling the
second click, clear any prior timer before creating a new one, and add a cleanup
effect that clears timeoutId.current (or flips mounted to false) so send is
never invoked after unmount.
- Around line 36-50: In the touches === 3 branch the code zeroes both axes when
one threshold is hit, so a diagonal swipe drops the second direction; update the
logic in the swipe handling inside the touches === 3 block (where
swipeAccumulator.current, SWIPE_THRESHOLD and send are used) to only reset the
axis that triggered the send (i.e., set swipeAccumulator.current.x = 0 when
sending an x swipe and swipeAccumulator.current.y = 0 when sending a y swipe) so
the other axis value is preserved and can still trigger its own send.

In `@src/server/InputHandler.ts`:
- Around line 47-62: Wrap each switch case body in InputHandler.ts inside its
own block to prevent scope leakage for block-scoped declarations: for the
'scroll' case (where const invert is declared) and the 'zoom' case (and any
other cases declaring const/let), surround the case's statements with { ... } so
that const invert and other variables are block-scoped to their case; update the
case labels for 'scroll' and the 'zoom' handling in the switch inside the
InputHandler class (or function) accordingly, ensuring no identifiers like
invert are declared twice across sibling cases.
- Around line 81-109: The 'swipe' case in InputHandler.ts risks leaving
modifiers pressed if keyboard.type() throws; wrap each modifier sequence in a
try/finally so that any pressed keys are always released — for example, after
calling keyboard.pressKey(Key.LeftSuper) and keyboard.pressKey(Key.LeftControl)
ensure a finally block calls keyboard.releaseKey(Key.LeftControl) and
keyboard.releaseKey(Key.LeftSuper); do the same for the other branches that
press LeftSuper (up/down/right) so every pressKey has a matching releaseKey in a
finally block around keyboard.type() calls.

In `@src/hooks/useTrackpadGesture.ts`:
- Around line 21-47: onDrag currently ignores drags when maxFingers.current >= 3
so three-finger swipe gestures are dropped; implement a branch in the onDrag
handler that detects three-finger gestures by accumulating scaledDx/scaledDy
into a three-finger gesture accumulator (e.g., threeFingerDelta or similar
state), apply a configurable threshold to determine direction
(left/right/up/down) and then call send(...) with the appropriate gesture event
(e.g., 'switch-desktop' / 'task-view' / 'show-desktop' or a single
'three_finger_swipe' with direction payload), and ensure the accumulator is
reset on drag end (onDrag end handler) and that sensitivity, maxFingers.current,
and scrollMode logic remain unchanged; if three-finger behavior was
intentionally omitted, update the PR description instead.

In `@src/hooks/useTrackpadGesture.ts`:
- Around line 28-52: The onDrag handler in useTrackpadGesture is using the
per-frame delta value to detect if movement exceeds TAP_MOVE_THRESHOLD, which
causes slow drags with small frame-by-frame movements to be incorrectly
identified as taps. Replace the threshold check that uses delta (obtained from
destructuring the delta property) with a check using the cumulative movement
value instead. Extract movement from the gesture event parameter and use
Math.abs(movement[0]) and Math.abs(movement[1]) in the comparison against
TAP_MOVE_THRESHOLD, while continuing to use delta for the scroll and move event
payloads.
- Around line 54-72: The bug is that touchCountRef is only updated in onDrag so
zero-movement taps read a stale value; update touchCountRef when pointers start
by capturing the current pointer/finger count in onPointerDown (or onTouchStart)
so onPointerUp uses the correct value; locate touchCountRef, onPointerUp and
onDrag in useTrackpadGesture.ts and add logic in onPointerDown (or the gesture
library's touch-start handler) to set touchCountRef.current to the active
pointer count before computing button and calling send({type: 'click', ...})
using TAP_TIME for tap detection.

In `@src/routes/trackpad.tsx`:
- Around line 50-55: onLeftClick and onRightClick currently call send(...) with
press: true and never send a release, leaving buttons held on the server; update
those callbacks to mirror the tap handler pattern in useTrackpadGesture.ts by
sending the press=true event immediately via send({ type: 'click', button:
'left'|'right', press: true }) and then scheduling a release with a short
setTimeout that calls send({ type: 'click', button: 'left'|'right', press: false
}); ensure you reference the existing send function and the same delay
value/pattern used by the tap handler to keep behavior consistent.